Hi, I'm using the template batchserver.dxl from API Manual with Python socket. "i_data_sent = s.send(byte_send_text)" the number of bytes sent correspond to my intend, but unfortunately i get error message in return.
after error analyses i found out that eval_ processes only first 2000 characters being sent for execution by the DXL interpreter.
is there any limit parameters to change this behavior or what have to consider in my socket implementation? skabantsov@mail.ru - Fri Sep 21 04:36:46 EDT 2018 |
Re: DXL eval_ string limit So there should definitely not be a limit to eval_ (can be easily tested) ... But you might have a fragmented package here, that your python socket sends data fragmented to 2000 bytes packages, which the DXL server might not be able to handle. If I were you I would not choose the DXL Batchserver to communicate with DXL. Network support in DXL is just too bad. You could use a file based communication approach which will also ensure, that your memory does not pile up with messages. In any case you should try to have your python socket send the whole code in one package and see if it changes behaviour. Note that network package size can be limited on some router/gateways. Regards, Mathias
|